#even worse is there's a legacy database and a modern database we use and locations are stored on both

[pancakeke]

a couple weeks back dev made a big update to one table. it really pissed me off because it's used by almost everything I write, and I have to filter it by excluding what I know I don't need rather than including what I do since everyone has permissions on our site to silently add rows to this thing.

one guy in dev made a comment about my complaints saying that if their update was such a big problem then maybe I should be writing more robust queries. but then also he said all I needed to do to exclude the new data was to filter by one column. which did not exist before this update. so how could I have future-proofed anything dude.

I think he was implying that I was filtering by names rather than IDs, which I wasn't cause that's nuts. but also our forecast tables show component inventory locations as names only. no mention of location IDs. these aren't views too, they're actual tables. knowing the inventory location is critical and needs to join to other tables to make anything of value. don't talk down to me if that's how your dept is setting things up.